Skip to content

chore(main): release 1.10.3 - #79

Merged
ivanmilevtues merged 1 commit into
mainfrom
release-please--branches--main--components--codeboarding-action
Aug 10, 2026
Merged

chore(main): release 1.10.3#79
ivanmilevtues merged 1 commit into
mainfrom
release-please--branches--main--components--codeboarding-action

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.10.3 (2026-08-10)

Bug Fixes

  • use stable PR route for webview links (#75) (e2f8a71)

This PR was generated with Release Please. See documentation.

@ivanmilevtues
ivanmilevtues merged commit 1933cbf into main Aug 10, 2026
@ivanmilevtues
ivanmilevtues deleted the release-please--branches--main--components--codeboarding-action branch August 10, 2026 23:31
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e1f2d0646f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@@ -1,3 +1,3 @@
{
".": "1.10.2"
".": "1.10.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Release the breaking action as v2.0.0

This release bumps the manifest to 1.10.3, so the release workflow will create a v1.10.3 release and then force-move v1 to it via .github/workflows/release-please.yml:62-68. The current tree already includes 474d40a feat!(action): simplify v2 flow to CLI incremental/full contract (#69) with a BREAKING CHANGE and README examples now telling users to pin @v2, so publishing this code as a 1.x release would silently upgrade existing @v1 consumers onto the v2 contract. Please cut/resync this as 2.0.0 (or resync the manifest after any manual v2 release) before publishing.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant